Collaborative workflow through messaging conversations

ABSTRACT

A networked application and email application were described herein that provide for an intuitive system by which users can participate in collaborative workflow relating to a network document. In one implementation, a system includes a messaging server component to provide messaging services and an application server component to provide a networked application. The application server component interacts with the messaging server component in response to a user command to initiate collaboration on the network document. The interaction with the messaging server component includes providing a link that refers to a version of the network document as created or edited by the user.

RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.14/658,881, filed Mar. 16, 2015, which is a continuation of U.S.application Ser. No. 14/023,696, filed Sep. 11, 2013, which is acontinuation of U.S. application Ser. No. 13/615,852, filed Sep. 14,2012, which is a continuation of U.S. application Ser. No. 13/359,157,filed Jan. 26, 2012, which is a continuation of of U.S. application Ser.No. 11/278,347, filed Mar. 31, 2006, the entire contents of each ofwhich are hereby incorporated by reference.

BACKGROUND

A. Field of the Disclosure

The present disclosure relates generally to collaboration among users ofa network application, and more specifically, to collaboration throughemail or chat programs.

B. Description of the Related Art

Existing office productivity applications, such as spreadsheet and wordprocessor applications, tend to be software programs that executelocally on a computer system of a single user. The documents produced bysuch a system can be difficult to distribute and difficult to modify orcollaborate on when working in a group environment.

Networked versions of these applications tend to provide a more suitableplatform for collaboration among multiple users. Different ones of theusers may edit and save their edits to a copy of a document at a centralstorage location. With such networked applications, it is desirable toprovide users the ability to initiate and participate in collaborativeworkflow in a manner that is convenient and conceptually simply for theusers.

SUMMARY

One aspect is directed to a method that includes providing a networkedapplication to a number of users, where the networked application isconfigured to facilitate generation of a network document. The methodfurther includes facilitating providing a messaging interface inresponse to a request from a user of the networked application to send amessage relating to collaboration on the network document. Further, themethod includes pre-populating the messaging interface with a subject ofthe message determined based on a subject of a previous message in athread of messages sent relating to collaboration on the networkdocument, and a link that references a version of the document ascreated or edited by the user.

Another aspect is directed to a system including a messaging servercomponent to provide messaging services and an application servercomponent. The application server component provides interacts with themessaging server component in response to a user command to initiatecollaboration on a network document based on sending of a message tocollaborators of the networked document. The collaborators are assigneddefault editing privileges for the network document based on how theuser addresses the collaborators in the message. The interaction withthe messaging server component includes providing a link that refers toa version of the network document as created or edited by the user.

Yet another aspect is directed to a method that includes receiving arequest to initiate collaboration on a network document; providing anemail interface in response to the request, the email interfaceincluding a “To:” field and a “CC:” field; and generating a group ofcollaborators for the network document based on user email addressesentered into the “To:” field and the “CC:” field. The group ofcollaborators are assigned default editing privileges by assigningcollaborators addressed in the TO field as having editing privileges andassigning collaborators addressed in the CC field as being limited toviewing the networked document.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate an embodiment of the inventionand, together with the description, explain the invention. In thedrawings,

FIG. 1 is a diagram illustrating a conceptual example of collaborativeworkflow relating to a document;

FIG. 2 is a diagram of an exemplary system in which concepts consistentwith the principles of the invention may be implemented;

FIG. 3 is a diagram of an exemplary computing device, such as one of thecomputing devices shown in FIG. 2;

FIG. 4 is a diagram illustrating an exemplary implementation of anonline spreadsheet application;

FIG. 5 is a diagram of an exemplary interface presented to a client bythe online spreadsheet application shown in FIG. 4;

FIG. 6 is a flow chart illustrating exemplary operations forimplementing collaborative workflow through threaded email messages;

FIG. 7 is a diagram of an exemplary email interface;

FIG. 8 is a diagram of another exemplary email interface;

FIGS. 9A, 9B, and 9C are diagrams illustrating additional exemplaryemail interfaces.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The detailed description does not limit the invention.

Overview

Implementations consistent with the principles of the invention relateto collaborative workflow in which different versions of a document arereferenced within messages of a threaded email or chat system. Users ofa set of threaded email or chat messages are able to quickly see thehistory of changes made to the collaborative document, potentially alongwith comments relating to changes made by the collaborators to thedocument.

One example of collaborative workflow relating to a document, such as aspreadsheet document organized in an email thread, is illustrated inFIG. 1. An email thread 110 is shown in FIG. 1 as an exemplary exchangeof five email messages 115-1 through 115-5 between four users. The emailmessages may be grouped to obtain the “thread” of email messages shownin FIG. 1 by an email client designed to group and display relatedemails together. An example of such an email client is the known Gmailclient, from Google Incorporated, which keeps track of individualthreads or “conversations” (an original message, along with all thereplies to that message), and allows users to view the emails related toa specific conversation.

In the example shown of FIG. 1, email 115-1 is the initial emailrequesting that recipients of the email make changes to a collaborativedocument that is referenced by a link 120 in email 115-1. The recipientsof email 115-1 may click on link 120 to open an editable version of thedocument. In this example, all three of the recipients of email 115-1(Jack, Jill, and Xavier) responded to email 115-1. Jack responded (email115-2) to say that he had no changes. Jill responded (email 115-3) andnoted that she made some changes to the document. The version of thedocument that includes Jill's changes is referenced by link 122 ofJill's email. Xavier responded (email 115-4) and noted that he also madesome changes to the document. The version of the document that includesXavier's changes is referenced by link 124 of email 115-4.

The four correspondents associated with thread 110 (i.e., Jim, Jack,Jill, and Xavier) can conveniently view email thread 110. Consistentwith an aspect of the invention, Jim, for example, may easily view thedifferent versions of the edited document by respectively clicking onlinks 120, 122, and 124. In some implementations, Jim may be able toeasily accept or reject the different changes made by Jill and Xavier.Because most people use an email application, providing forcollaborative workflow via email thread 110 gives users the ability toeasily and intuitively initiate and participate in collaborativeworkflow.

System Description

FIG. 2 is a diagram of an exemplary system 200 in which conceptsconsistent with the principles of the invention may be implemented.System 200 may include multiple clients 210 that can connect to servers,such as servers 220 and 240, via a network 250. Network 250 may includea local area network (LAN), a wide area network (WAN), a telephonenetwork, such as the Public Switched Telephone Network (PSTN), anintranet, the Internet, or a combination of networks. Two clients 210and two servers 220 and 240 are illustrated as connected to network 250for simplicity. In practice, there may be more clients and/or servers.Also, in some instances, a client may perform one or more functions of aserver and a server may perform one or more functions of a client.

A client 210 may include a device, such as a personal computer, a laptop computer, a wireless telephone, a personal digital assistant (PDA),or another type of computation or communication device. Users of clients210 may access or receive information from servers 220 and 240.

Server 220 may generally interact with clients 210 such that clients210, in conjunction with server 220, interact with a network-basedapplication, such as a network spreadsheet or word processingapplication. Server 220 may include software, labeled as applicationserver component 225, to assist in implementing the network application.Documents created by users of clients 210 may be stored by server 220in, for example, storage media such as database 230. Althoughillustrated as a single device in FIG. 2, server 220 may be implementedas, for example, a single computing device or as multiple distributedcomputing devices. One of ordinary skill in the art will appreciate thatwhether a device is functioning as a server or a client often depends onthe specific application being implemented. That is, whether a computingdevice is operating as a client or a server may depend on the context ofthe role of the computing device within the application. Therelationship of client and server arises by virtue of computer programsrunning on the respective computers and having a client-serverrelationship to each other.

Server 240 may generally interact with clients 210 to assist clients 210in sending and receiving email. Clients 210 may, for example, connect toserver 240 via web browsers 215 or via separate email client programs(not shown) to upload emails to server 240 that are to be sent to otherusers or to download received emails. Server 240 may include software,labeled as email server component 245, that provides the functionalityfor server 240 to act as an email server. In alternativeimplementations, server 220 may function as an Instant Message (IM)server, or as another type of messaging platform. Server 240, althoughillustrated as a single device, may be implemented as, for example, asingle computing device or as multiple distributed computing devices.

The interaction of clients 210 with servers 220 or 240 may be throughbrowser programs 215 at clients 210. For example, the networkedapplication implemented by application server component 225 may be anonline spreadsheet application that functions as a web application thatruns within browsers 215. In this manner, clients 210 may not berequired to install any spreadsheet specific software to use the onlinespreadsheet at client 210. Browser programs are well known and arewidely available in the art. When browsers or browser programs arediscussed herein, these terms are intended to refer to any program thatallows a user to browse markup documents (e.g., web documents),regardless of whether the browser program is a stand alone program or anembedded program, such as a browser program included as part of anoperating system.

Exemplary Computing Device Architecture

FIG. 3 is an exemplary diagram of computing device 300, such as one ofclients 210, server 220, or server 240. Computing device 300 may includea bus 310, a processor 320, a main memory 330, a read only memory (ROM)340, a storage device 350, an input device 360, an output device 370,and a communication interface 380. Bus 310 may include a path thatpermits communication among the components of computing device 300.

Processor 320 may include any type of processor, microprocessor, orprocessing logic that interprets and executes instructions. Main memory330 may include a random access memory (RAM) or another type of dynamicstorage device that may store information and instructions for executionby processor 320. ROM 340 may include a ROM device or another type ofstatic storage device that may store static information and instructionsfor use by processor 320. Storage device 350 may include a magneticand/or optical recording medium and its corresponding drive.

Input device 360 may include a mechanism that permits a user to inputinformation to computing device 300, such as a keyboard, a mouse, a pen,voice recognition and/or biometric mechanisms, etc. Output device 370may include a conventional mechanism that outputs information to theuser, including a display, a printer, a speaker, etc. Communicationinterface 380 may include any transceiver-like mechanism that enablescomputing device 300 to communicate with other devices and/or systems.For example, communication interface 380 may include mechanisms forcommunicating with another device or system via a network, such asnetwork 250.

Application server component 225 and email server component 245 may beimplemented in software and stored in a computer-readable medium, suchas memory 330. A computer-readable medium may be defined as one or morephysical or logical memory devices and/or carrier waves.

The software instructions defining application server component 225 andemail server component 245 may be read into memory 330 from anothercomputer-readable medium, such as data storage device 350, or fromanother device via communication interface 380. The softwareinstructions contained in memory 330 cause processor 320 to performprocesses that will be described later. Alternatively, hardwiredcircuitry may be used in place of or in combination with softwareinstructions to implement processes consistent with the presentinvention. Thus, implementations consistent with the principles of theinvention are not limited to any specific combination of hardwarecircuitry and software.

Application Server Component 225

As previously mentioned, application server component 225 can enableclients 210 to use a networked application, such as an onlinespreadsheet application, an online word processor application, oranother type of online application. Before describing operationsconsistent with aspects of the invention relating to collaborativeworkflow in additional detail, it will be helpful to describe an examplenetworked application implemented by application server component 225.Application server component 225 will particularly be described asimplementing an online spreadsheet application, although applicationserver component 225 can more generally be used to implement anynetworked application that allows collaboration among multiple users.

The online spreadsheet application may be implemented as a distributedweb application in which portions of the application execute at one ormore of clients 210 and at server 220. More specifically, clients 210that wish to use the online spreadsheet application may request thespreadsheet application from server 220. In response, server 220 maytransmit portions of the spreadsheet application to clients 210 forlocal execution at clients 210. The online spreadsheet application maythus execute as a distributed application across server 220 and one ormore of clients 210.

FIG. 4 is a diagram illustrating an exemplary implementation of theonline spreadsheet application in additional detail. Application servercomponent 225 may include a front-end component 426 and a back-endcomponent 427. Front-end component 426 may include a web and/or XMLserver that interfaces with clients 210. For example, front-endcomponent 426 may receive HTTP requests from clients 210 and transmitXML data to clients 210. Back-end component 427 may perform the moresubstantive processing related to the spreadsheet application, such asthe calculation of functions required to update a spreadsheet.

Portions of the online spreadsheet application may also execute withinclients 210. For example, within browser 215, the online spreadsheetapplication may be conceptualized as including a client engine 416 and auser interface 417. Client engine 416 may be implemented using, forexample, Javascript that is downloaded from server 220 when needed byclient 210. User interface 417 may provide the final user interface thatis displayed in browser 215 based on, for example, HTML (hyper-textmarkup language) and CSS (cascading style sheets) data supplied fromclient engine 416.

User interface 417 and client engine 416 together act to reduce thestart-stop start-stop nature of traditional browser-based webapplications, as client engine 416 adds a client-side layer that canhandle many of the user interactions with user interface 417. Instead ofloading a web page at the start of a user session, browser 215 may loadclient engine 416 from server 220 (or, alternatively, from a localcache). Client engine 416 may be responsible for both rendering theinterface the user sees and communicating with server 220 on the user'sbehalf. Client engine 416 allows the user's interaction with the onlinespreadsheet application to happen asynchronously, i.e., independent ofcommunication with server 220.

In one implementation, the client-side operation of the onlinespreadsheet application may be implemented using the known AsynchronousJavaScript And XML (AJAX) web development techniques, although one ofordinary skill in the art will recognize that other technologies couldbe used.

FIG. 5 is a diagram of an exemplary interface 500 presented to a clientby an online spreadsheet application. Interface 500 may be shown withinbrowser 215 of a client 210. Interface 500 may include a control row511, a column heading row 512, and a number of data rows 513 labeled onethrough eight. Control row 511 may include a field 521 that displays thecurrently active cell (e.g., cell D4 in the example shown in FIG. 5) anda formula field 522 in which the user may enter formulas or otherspreadsheet operations. Column heading row 511 includes the columnheadings labeled “A” through “H”. Users can specify a particular cell ininterface 500 by a combination of a column heading and a row heading.Cell D1, for example, includes the value “$9.00”.

Through interface 500, a user can, for example, enter values or formulasinto the spreadsheet cells and perform formatting operations relating tothe spreadsheet. In response, client engine 416 interacts with and makesrequests of application server component 225 as necessary. As shown inFIG. 5, a user has entered the text “Expenses for the Trip:” into cellB1 and entered dollar values into cells D1, D2, and D3. Cell D4 iscurrently the active cell (shown by the bold lines surrounding thiscell). The user has entered the formula “=sum(D1:D3),” which is shown informula field 522, and which directs the spreadsheet to sum the valuesin cells D1 through D3 and to write the result into cell D4. Further, asis also shown in FIG. 5, the user has modified the width of columns “F”and “G.” The user may do this by, for example, dragging the columnseparation line between columns “F” and “G” in the desired direction.

Interface 500 may also provide other commands relating to thespreadsheet document. Interface 500 may include a “save” button 535 anda “share” button 540. Selecting save button 535 may cause thespreadsheet document to be saved to database 130. The spreadsheetdocument may thus be accessible by the user (or by other users) from anycomputing device connected to network 250. Database 130 may storemultiple versions of the spreadsheet document. In this manner, the usermay be able to view the spreadsheet document at different save points inthe development of the document.

Share button 540 may provide an interface through which a user, such asa creator of the spreadsheet document, can share the spreadsheetdocument with other collaborators. Functionality associated with sharebutton 540 consistent with an aspect of the invention, in which a usercan initiate collaborative workflow through a threaded messagingapplication, will be described in more detail below.

The online spreadsheet application may provide for collaboration amongmultiple users working on a single spreadsheet. For example, multipleusers may simultaneously edit a spreadsheet and view the edits of eachof the users. When one user edits a particular cell of the spreadsheet,the edit may be transmitted to application server component 225 and thenforwarded to other collaborating users that are also editing or viewingthe spreadsheet. In this manner, multiple users may collaborate,potentially in real-time (or in near real-time), on a singlespreadsheet. When performing real-time collaboration between multipleusers, the online spreadsheet application may implement a conflictresolution scheme to handle situations in which different users attemptto simultaneously modify a spreadsheet cell. For example, the onlinespreadsheet application may give priority to certain users when decidingconflicts or the online spreadsheet application may lock a cell whenevera collaborator begins to edit the cell.

In one implementation, the parties that may view and collaborate on aparticular spreadsheet application may be specified. For example,different users may be given privileges to do one or more of thefollowing: edit the spreadsheet, view the spreadsheet only, editdesignated parts of the spreadsheet, or add additional users to the listof possible collaborators. Certain users may be able to edit certainparts of the spreadsheet, while other designated cells or regions ofcells will remain “locked” to those users such that the users can viewbut not edit the locked cells.

In some implementations, users may be able to configure the presentationof interface 500 to in some manner illustrate which users have madewhich edits. For example, changes made by different users may be shownin a different font or different color for each user. Alternatively oradditionally, when a user mouses over or in some way selects a cell, anindication of the collaborator who last edited the cell may be shown.

The above-described functions and operations that are allowable by theonline spreadsheet application are exemplary. Through spreadsheetinterface 500, the online spreadsheet application may permit a user toperform numerous operations that are generally recognized as beingconsistent with a spreadsheet application.

Collaborative Workflow

Consistent with an aspect of the invention, application server component225 and email server component 245 may interact with one another toimplement collaborative workflow through threaded email or chatmessages.

FIG. 6 is a flow chart illustrating exemplary operations forimplementing collaborative workflow through threaded email messages. Auser may begin by creating or editing a network document, such as anetwork spreadsheet document, using application server component 225(act 601).

At some point the user may wish to make the network document availableto other collaborating users. The user may initiate collaborationthrough an appropriate command in the network application, such as acommand that initiates collaboration through a message, such as an emailmessage (act 602). In the exemplary spreadsheet interface 500, forexample, the user may select share button 540 to initiate collaboration.In response, application server component 225 may contact email servercomponent 245 and initiate an email message on the users behalf thatcontains a link to the network document (act 603). In oneimplementation, the user may have previously registered with applicationserver component 225 to provide the user's email account information(e.g., email provider, login name, etc.) to application server component225. In other implementations, application server component 225 andemail server component 245 may be integrated in some manner, such as byboth being part of a single “office suite” of applications or by beingintegrated by virtue of the control of both being with the same party.

FIG. 7 is a diagram of an exemplary email interface 700 that applicationserver component 225 may present to a user when sending an email inresponse to the user selecting share button 540. Email interface 700 maybe presented to the user as, for example, a pop-up window or a sidebarin spreadsheet interface 500. In some implementations, interface 700 maybe generated by email server component 245 on behalf of, or in responseto a signal from, application server component 225. As shown, theexemplary email interface 700 may include a recipient section 710 and amessage section 720. In recipient section 710, the user may enter theintended collaborators of the spreadsheet, such as by entering the emailaddresses of the collaborators. In some implementations, the user mayalso be able to configure the permissions that are granted to each ofthe collaborators. For example, some of the collaborators may be grantedpermission to edit the spreadsheet while other of the collaborators maybe limited to viewing the spreadsheet. In one possible implementation,the recipients in the “TO:” field may be initially granted full editingprivileges while the recipients in the “CC:” or “BCC:” field may beinitially granted only viewing privileges. The user, if desired, maymodify these initially granted privileges.

In message section 720, the user may enter a message that is to be sentto the recipients with the email. Message section 720 may bepre-populated by application server component 225 with a link 725 thatreferences the current version of the spreadsheet (i.e., the version ofthe spreadsheet that is being emailed). Link 725 will be mailed to thecollaborators and can be clicked on by the collaborators to open a copyof the spreadsheet document at client 210 associated with the clickingrecipient. Link 725 may include a uniform resource locator (URL) thatrefers to application server component 225 on server 220 and includes astring identifying the current version of the spreadsheet.

As other collaborators edit and save changes to the spreadsheetdocument, they may send a new message from application server component225 using share button 540 (act 604). Each new message may be sent inthe manner described above with reference to the email sent using emailinterface 700. More particularly, FIG. 8 is a diagram of an exemplaryemail interface 800 that application server component 225 may present toa user that has edited the collaborative document.

Email interface 800 is similar to email interface 700, except in FIG. 8,the sender (Xavier) has edited the spreadsheet and is sending a link 825to each of the collaborators. Link 825, as with link 725, may have beenassigned by application server component 225. Link 825 may reference adifferent version of the spreadsheet document than link 725 (i.e., theversion of the spreadsheet document as edited by Xavier). A user openingthe spreadsheet document by selecting link 825 may thus view a differentversion of the spreadsheet document than if the spreadsheet document wasopened by selecting link 825. Application server component 225 maypre-populate various fields in the email interface based on the contentof previous collaboration related messages for the application. Forexample, the “Subject:” field and the “To:” field may be pre-populatedbased on the subject and based on the previous recipients of the emailmessage, respectively. The pre-populated data may correspond to datapre-populated by a conventional email system in replying to a message.

In some implementations, instead of initiating a message via sharebutton 540, users may send a message regarding document collaborationthrough email server component 245, such as by replying to a previousmessage relating to device collaboration. For example, the message shownin FIG. 8 (i.e., email message 115-4 in FIG. 1) may have been initiatedby the sender (Xavier) replying to the message shown in FIG. 7 (i.e.,email message 115-1 in FIG. 1) via email server component 245. Emailserver component 245 may set link 825 either by contacting applicationserver component 225 or by the sender directly pasting or typing link825.

Exemplary Series of Workflow Emails

Collaborative workflow using a threaded email application will next bedescribed with reference to FIGS. 9A and 9B.

FIG. 9A is a diagram illustrating an exemplary email interface 900 of anemail application, such as an email application provided by email servercomponent 245. Email server component 245 may group related messagesinto threads (conversations). Email server component 245 may determinewhen different messages are related based on, for example, common orsimilar message text, recipients, and/or subject header text. As shownin FIG. 9A, email interface 900 may include a list of messages 910 thatare currently in the “inbox” of the user. Each item in list 910 may bedisplayed as a “From:” field 915 and a “Subject:” field 920. In thisexample, the second message, message 925, in list of messages 910represents a thread of messages. This is illustrated in email interface900 by the list of senders (“Jack, Jill, Xavier, me”) associated withmessage 925 and by the number in parenthesis (“(5)”) after the list ofsenders, which indicates the number of messages in the thread.

When a user selects threaded message 925, such as by selecting themessage via a mouse click, the email application may show a moredetailed view of the message thread. FIG. 9B is a diagram illustratingan exemplary email interface 940 illustrating five email messages inmessage thread 925. Message thread 925 is similar to the series ofmessages shown in FIG. 1. As shown in FIG. 9B, however, the user haschosen to minimize the view of messages 115-1 and 115-2. In thisexample, the user may toggle between a minimized view of a message and a“normal” view of the message by selecting the header portion of themessage with a pointing device.

As previously mentioned, selecting one of links 122 or 124 may open thenetwork document corresponding to the link. In this example, multipleversions of a spreadsheet application may be stored by applicationserver component 225. Selecting a link 122 or 124 may cause browser 215to contact application server 225 and initiate an instance of thenetwork spreadsheet application. Application server component 225 maydetermine the particular version of the spreadsheet based on the contentof the link. In this example, the text “chart123.htm?version=2” refersto the spreadsheet document saved by Jill and the text“chart123.htm?version=3” refers to the spreadsheet document saved byXavier.

FIG. 9C is a diagram illustrating an exemplary email interface 960illustrating email messages in message thread 925. In thisimplementation, some or all of the spreadsheet document may, instead ofbeing presented as a selectable “link,” may be shown as an inline (e.g.,an embedded) version of the spreadsheet document. In other words, theonline application may be implemented within the email application. Inimplementations in which the email application executes within a browserprogram, the online application may execute within a frame or othersection of the email application. In exemplary interface 960, email115-3 is shown as including a section 965 that includes an embeddedversion of the spreadsheet document. In some implementations, whether toshow the spreadsheet document as a selectable link or as an embeddedversion of the document may be a user-settable option.

Through the email application illustrated in FIGS. 9A, 9B, and 9C, andthrough a networked application, such as one from application servercomponent 225, a user can easily initiate and participate incollaborative workflow. All participants in the collaborative workflowcan easily view and open older versions of the network document beingcollaborated upon. Additionally, application server component 225 mayinclude functionality that allows a user, such as the initial creator ofthe network document, to automatically integrate changes made inselected versions of the network document into a single “master” or“final” document.

Although the collaborative workflow described above was primarilydescribed in the context of a networked application and an emailapplication, the concepts described above may also be applicable toother types of messaging systems, such as an instant message (IM) chatsystem.

Conclusion

A networked application and email application were described herein thatprovide for an intuitive system by which users can participate incollaborative workflow relating to a network document.

The foregoing description of exemplary embodiments of the inventionprovides illustration and description, but is not intended to beexhaustive or to limit the invention to the precise form disclosed.Modifications and variations are possible in light of the aboveteachings or may be acquired from practice of the invention. Forexample, while the computer systems described herein was described asbeing used to implement an online spreadsheet, they could also be usedto create other collaborative documents, such as a wiki or table.

Moreover, while series of acts have been described with regard to FIG.6, the order of the acts may be varied in other implementationsconsistent with the invention. Moreover, non-dependent acts may beimplemented in parallel.

It will also be apparent to one of ordinary skill in the art thataspects of the invention, as described above, may be implemented in manydifferent forms of software, firmware, and hardware in theimplementations illustrated in the figures. The actual software code orspecialized control hardware used to implement aspects consistent withthe principles of the invention is not limiting of the invention. Thus,the operation and behavior of the aspects of the invention weredescribed without reference to the specific software code—it beingunderstood that one of ordinary skill in the art would be able to designsoftware and control hardware to implement the aspects based on thedescription herein.

Further, certain portions of the invention may be implemented as “logic”or a “component” that performs one or more functions. This logic mayinclude hardware, such as an application specific integrated circuit ora field programmable gate array, software, or a combination of hardwareand software.

No element, act, or instruction used in the description of the inventionshould be construed as critical or essential to the invention unlessexplicitly described as such. Also, as used herein, the article “a” isintended to include one or more items. Where only one item is intended,the term “one” or similar language is used. Further, the phrase “basedon” is intended to mean “based, at least in part, on” unless explicitlystated otherwise.

1-16. (canceled)
 17. A method comprising: executing a messagingapplication; receiving a message that is associated with the messagingapplication; responsive to the messaging application opening themessage, executing, without user interaction, a second application thatoutputs an embedded version of a document for inline display within asection of the message, the second application being different from themessaging application; responsive to receiving user input from a firstuser to modify the embedded version of the document within the sectionof the message, generating a modification to the document; andtransmitting, to at least one computing device, the modification to thedocument, such that the modification is accessible to a second userdifferent from the first user.
 18. The method of claim 17, where themessage includes a link to a second version of the document.
 19. Themethod of claim 17, further comprising: sending a request for one ormore portions of the second application; responsive to sending therequest, receiving the one or more portions of the second applicationfor execution.
 20. The method of claim 17, wherein the first user isassociated with a first set of privileges associated with the document,and wherein the second user is associated with a second set ofprivileges associated with the document, the first set of privilegesbeing different than the second set of privileges.
 21. The method ofclaim 17, wherein the messaging application is executed within a browserprogram, wherein the section of the message is a frame, and wherein thesecond application is executed to output the embedded version of thedocument for inline display within the frame.
 22. The method of claim17, wherein the message is an email message, and wherein the messagingapplication is an email application.
 23. The method of claim 17, whereinthe message is an instant message, and wherein the messaging applicationis an instant messaging application.
 24. A computing device comprising:one or more processors; a communication interface; and a non-transitorycomputer-readable medium storing one or more instructions that, whenexecuted, cause the one or more processors to: execute a messagingapplication; receive, via the communication interface, a message that isassociated with the messaging application; responsive to the messagingapplication opening the message, execute, without user interaction, asecond application that outputs an embedded version of a document forinline display within a section of the message, the second applicationbeing different from the messaging application; responsive to receivinguser input from a first user to modify the embedded version of thedocument within the section of the message, generate a modification tothe document; and transmit, via the communication interface and to atleast one other computing device, the modification to the document, suchthat the modification is accessible to a second user different from thefirst user.
 25. The computing device of claim 24, where the messageincludes a link to a second version of the document.
 26. The computingdevice of claim 24, wherein the one or more instructions stored by thenon-transitory computer-readable medium further cause the one or moreprocessors to: send, via the communication interface, a request for oneor more portions of the second application; and responsive to sendingthe request, receive, via the communication interface, the one or moreportions of the second application for execution.
 27. The computingdevice of claim 24, wherein the first user is associated with a firstset of privileges associated with the document, and wherein the seconduser is associated with a second set of privileges, the first set ofprivileges being different than the second set of privileges associatedwith the document.
 28. The computing device of claim 24, wherein themessaging application is executed within a browser program, wherein thesection of the message is a frame, and wherein the second application isexecuted to output the embedded version of the document for inlinedisplay within the frame.
 29. The computing device of claim 24, whereinthe message is an email message, and wherein the messaging applicationis an email application.
 30. The computing device of claim 24, whereinthe message is an instant message, and wherein the messaging applicationis an instant messaging application.
 31. A non-transitorycomputer-readable medium storing one or more instructions that, whenexecuted by at least one processor, cause one or more processors to:execute a messaging application; receive a message that is associatedwith the messaging application; responsive to the messaging applicationopening the message, execute, without user interaction, a secondapplication that outputs an embedded version of a document for inlinedisplay within a section of the message, the second application beingdifferent from the messaging application; responsive to receiving userinput from a first user to modify the embedded version of the documentwithin the section of the message, generate a modification to thedocument; and transmit, to at least one computing device, themodification to the document, such that the modification is accessibleto a second user different from the first user.
 32. The non-transitorycomputer-readable medium of claim 31, where the message includes a linkto a second version of the document.
 33. The non-transitorycomputer-readable medium of claim 31, wherein the one or moreinstructions further cause the one or more processors to: send a requestfor one or more portions of the second application; and responsive tosending the request, receive the one or more portions of the secondapplication for execution.
 34. The non-transitory computer-readablemedium of claim 31, wherein the first user is associated with a firstset of privileges associated with the document, and wherein the seconduser is associated with a second set of privileges, the first set ofprivileges being different than the second set of privileges associatedwith the document.
 35. The non-transitory computer-readable medium ofclaim 31, wherein the messaging application is executed within a browserprogram, wherein the section of the message is a frame, and wherein thesecond application is executed to output the embedded version of thedocument for inline display within the frame.
 36. The non-transitorycomputer-readable medium of claim 31, wherein the message is an emailmessage, and wherein the messaging application is an email application.